In Kepler.gl, geometries (Polygons, Points, LindStrings etc) can be embedded into CSV as a GeoJSON or WKT formatted string. (see here). This PR is to support WKB geometry column in CSV file. For example, the following CSV row contains a WKT geometry:

id,geom
2,POINT(1 2)

the following CSV row contains a WKB geometry in hex format:

id, geom
1,0101000000000000000000F03F0000000000000040

1. The WKB format is more efficient than the WKT for storing and processing geometry objects. e.g. the output of the geometry column in PostGIS is returned as WKB in hex format by default unless using e.g. ST_AsWKT
2. The WKB format keeps the precisions of the raw geometry data
3. The size of WKB in hex format is 2 times the size of WKB, however, it is usually smaller than WKT with complex geometries (linestrings, polygons etc. -- don't use WKB hex to store simple points : )

• guerry.geojson is 2 MB
• guerry_wkt.csv is 1.7 MB
• guerry_wkb.csv is 1.4 MB
• guerry.arrow is 705 KB

There is another wip PR to support Arrow/GeoArrow in Kepler.gl: #2